Securing a Private Channel

There are many ways to secure a channel. Security is often achieved at the expense of ease-of-use. UtoNet feels the best way to secure a channel is often to use invite-only mode, coupled with NickServ's AJOIN to join the channel automatically.

An Example Invite-Only Configuration

This example creates an invite-only channel where any user with VOP or higher status can invite themself with AJOIN. Your channel members will have to be registered.

In all the commands below, replace #channel with this channel name you have selected. Replace any underlined words or phrases as appropriate.

First, find an empty, unregistered channel. Confirm it is unregistered using /cs info #channel, then join and issue the following commands:

/cs register #channel password private
/cs set #channel mlock +inst
/cs set #channel secureops on
/cs set #channel restricted on
/cs set #channel private on
/cs levels #channel set invite 30

You should set a channel successor. Your successor will inherit ownership of the channel if you stop using IRC.
/cs set #channel successor successor-name

Add your members to the channel using this command. Repeat for each person:
/cs vop #channel add member-name

Tell your members to add this channel to their NickServ AJOIN list to automatically join the channel when they identify:
/ns ajoin add #channel

Alternatives: Key-Based Security

A channel key is just a password that is required to join your channel. It's not as secure as invite-only, since anyone in your channel can leak the password. Also someone could guess your channel key. You don't really have direct control over who can join your channel this way.

The upside is that it's easier for people who do not have a registered nickname to join your channel.

Set your key with:
/mode #channel +k your-key

You should also use ChanServ MLOCK to prevent people from seeing your channel in LIST and WHOIS commands
/cs set #channel mlock +nst

You should not MLOCK your key, since if your channel is empty, anyone can still join the channel and then see your key being set.

Alternatives: Security-Through-Obscurity

This is a pretty bad idea, and you should only do it if you really don't mind random people being able to wander into your channel.

MLOCK modes +nst to keep your channel from showing up in WHOIS responses and the channel LIST.

/cs set #channel mlock +nst

Anyone will be able to join your channel, if they have the name of the channel, or if they can guess it.